Method and system for tracking and reporting emissions

ABSTRACT

The present invention relates to methods and systems of tracking enterprise gas emissions such as greenhouse gas emissions. The systems and methods relate to collecting or entering data relating to one or more emissions source of an enterprise or an enterprise location, calculating emissions totals, and, according to certain embodiments, generating emissions reports.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.11/744,713 filed on May 4, 2007, which claims priority to U.S. PatentApplication No. 60/893,261, filed Mar. 6, 2007, entitled “EmissionsTracking and Reporting,” and further is a continuation-in-part of U.S.patent application Ser. No. 11/423,860, filed Jun. 13, 2006, entitled“Enterprise Energy Management System,” which is a continuation-in-partof U.S. patent application Ser. No. 10/768,957, filed Jan. 30, 2004,entitled “Enterprise Energy Management System,” which issued as U.S.Pat. No. 7,062,389 on Jun. 13, 2006, which claims priority to U.S.Patent Application No. 60/444,091, filed Jan. 31, 2003, entitled“Enterprise Energy Management,” all of which are hereby incorporatedherein by reference in their entireties. U.S. patent application Ser.No. 11/744,713, filed May 4, 2007, is also a continuation-in-part ofU.S. patent application Ser. No. 10/429,619, filed May 5, 2003, entitled“Refrigerant Loss Tracking and Repair,” which claims priority to U.S.Patent Application No. 60/432,120, filed Dec. 9, 2002, entitled“Refrigerant Loss Tracking and Repair,” both of which are herebyincorporated herein by reference in their entireties.

FIELD

This invention relates generally to a system and method for trackinggreenhouse gas emissions, and further can relate to recording and/orreporting such emissions. According to one embodiment, the invention canalso relate to tracking such emissions produced by an enterprise.

BACKGROUND

Gases that trap heat in the atmosphere are often called greenhouse gases(GHGs). GHGs are believed to be a significant contributor to the globalwarming phenomenon. Some GHGs such as carbon dioxide occur naturally andare emitted to the atmosphere through natural processes. Other GHGs arecreated and emitted solely through human activities. The principal GHGsthat enter the atmosphere because of human activities are: carbondioxide (CO2), methane (CH4), nitrous oxide (N20), and fluorinated gasessuch as hydrofluorocarbons, perfluorocarbons, and sulfur hexafluoride.In addition, GHGs can include at least some types of chlorinated gases.

Many governments are taking steps to reduce GHG emissions throughnational policies that include the introduction of emissions tradingprograms, voluntary programs, carbon or energy taxes, and regulationsand standards on energy efficiency and emissions. As a result of suchpolitical and legislative initiatives in the United States and abroad,organizations are increasingly required to track and report their GHGemissions. Such emissions tracking and reporting can be arduous when itmust be conducted for a multi-site organization or enterprise whichexists across a wide geography. For example, a large retail chain mayhave hundreds of sites across the United States, with each sitecontaining hundreds of sources of GHG emissions.

Accordingly, there is a need in the art for a system or method forexpeditiously and efficiently tracking and reporting the GHG emissions.

BRIEF SUMMARY

Certain embodiments disclosed herein relate to a network based emissionstracking system comprising a first database and a server. The firstdatabase includes a plurality of characteristics relating to anenterprise's direct emission sources and indirect emission sources. Theserver includes software for tracking emissions of the direct emissionsources and indirect emission sources based on the plurality ofcharacteristics.

Another embodiment relates to a method of tracking an enterprise'semissions. The method includes maintaining at a first database aplurality of characteristics relating to the enterprise's directemission sources and indirect emission sources and further includestracking with software emissions of the direct emission sources andindirect emission sources based on the plurality of characteristics.

A further embodiment relates to a method of tracking and reportingamounts of greenhouse gas emissions produced by an enterprise. Themethod includes gathering data corresponding to each of an enterprise'semission sources, storing the data in a database, calculating the amountof green house gas emissions produced by each emission source, andgenerating an emissions report that comprises the amount of greenhousegas emissions produced by a emission source or plurality of emissionsources.

While multiple embodiments are disclosed, still other embodiments willbecome apparent to those skilled in the art from the following detaileddescription, which shows and describes illustrative embodiments of theinvention. As will be realized, the invention is capable ofmodifications in various obvious aspects, all without departing from thespirit and scope of the inventions described herein. Accordingly, thedrawings and detailed description are to be regarded as illustrative innature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow chart illustrating the operation of a emissionstracking and reporting system in accordance with one embodiment.

FIG. 2 is a flow chart depicting a method of organizing and collectingemissions data, according to one embodiment.

FIG. 3 is a block diagram of an emissions tracking system configuration,in accordance with one embodiment.

FIG. 4 is a flow chart illustrating the collecting and entering ofemissions information into an emissions tracking system, in accordancewith one embodiment.

FIG. 5 is a flow chart illustrating a method of managing an invoice,according to one embodiment.

FIG. 5 is a flow chart illustrating a method of tracking and managingcarbon credits, according to one embodiment.

FIG. 7 is a flow chart illustrating the generating of an emissionreport, according to one embodiment.

DETAILED DESCRIPTION

The present invention relates to tracking emissions such as, forexample, greenhouse gas (“GHG”) emissions as defined above. Further, itis understood that the various systems and methods described herein canbe used to track a wide variety of different types of emissions.

FIG. 1 is a flow chart depicting the overall operation of a method andsystem for tracking emissions 10, according to one embodiment. Thesystem generally comprises collecting data and/or entering data into thesystem relating to emissions sources (block 12), calculating emissionstotals (block 14), and, according to certain alternative embodiments,generating emissions reports requested by a user on the basis of thestored emissions data (block 16). The system 10 can track the emissionsof each source of interest. In one embodiment, the system 10 tracks theemissions of each source at a particular location. Alternatively, thesystem 10 tracks the emissions of each emission source of each locationof an enterprise. The system 10, in accordance with another aspect, cangenerate reports detailing the amount of emissions produced by anemission source or group of emission sources, particularly the amount ofgreenhouse gases produced by each source, and more particularly theamount of carbon dioxide and carbon dioxide equivalents produced.

In one embodiment, the system 10 tracks all types of emissions from allkinds of emission sources. For example, in one embodiment, emissions caninclude emissions that originate from both direct and indirect emissionsources. Thus, in one embodiment, the system 10 tracks emissions fromboth direct and indirect sources. Alternatively, the system 10 can tracksolely the emissions from direct emission sources or solely theemissions from indirect emission sources.

Direct emission sources are those sources of emissions which are ownedor controlled by the enterprise. Generally, direct emission sourcescomprise four subtypes: mobile combustion sources, stationary combustionsources, manufacturing process sources, and fugitive emission sources.For example, a vehicle or building heater would be a direct emissionsource.

In contrast, indirect emission sources include those sources whichproduce emissions, in whole or in part, as a result of the enterprise'sactivities, and are owned or controlled by another entity. Indirectemission sources include, for example, any energy or other GHG emittingsources that are imported from a third party, such as importedelectricity, imported steam, imported heating, or imported cooling, allof which can also be referred to herein as “utilities.” Importedelectricity can include, but is not limited to, any electricity importedfrom one or more electric companies or other electricity providers. Inone embodiment, imported electricity can include electricity from aco-generation plant, which is an engine or plant that simultaneouslygenerates power and useful heat. Imported steam can include, but is notlimited to, any steam imported from one or more steam providers or powerplants. Imported heating can include, but is not limited to, any heatimported in any form from any heat provider. According to oneimplementation, imported heating can include steam or hot water importedfrom one or more heating providers. Imported cooling can include, but isnot limited to, any cooling imported in any form from any coolingprovider. In accordance with one aspect, imported cooling can includeimported chilled water or other media for air conditioning or other usesfrom one or more cooling providers.

Returning to direct emission sources, the mobile combustion sources arethose non-stationary assets of an enterprise that create emissions bymeans of fuel combustion, including, for example, automobiles,motorcycles, trucks, forklifts, boats, airplanes, constructionequipment, and the like. The stationary combustion sources are thosestationary assets of an enterprise that create emissions by means offuel consumption, including, for example, power plants, refineries,furnaces, heaters, and the like.

The manufacturing process sources include an enterprise's manufacturingor industrial processes that result in release of emissions. Thesesources may include, for example, the manufacturing of aluminum, iron,steel, refrigerants, ammonia, acids, and lime. The fugitive emissionssources include the assets of an enterprise that cause emissions to bereleased by means of unintentional release or leak, such as is common inair conditioning and refrigeration equipment, for example.

While specific examples of emission sources for each emission type andsubtype have been provided, the methods and systems discussed hereinanticipate the tracking of any type of emission from any emissionsource.

As an initial procedure according to one embodiment prior to collectionof emissions information (block 12), the emission sources of anenterprise to be monitored may be inventoried and an emission sourceidentifier created for each emission source to give it a trackableidentity. According to one embodiment, this approach provides a uniformnaming convention, such that the same emissions source is identified bythe same name or identification number each time it is entered into thesystem. In another embodiment, a set of appropriate data fields isassociated with each emissions source wherein each field has a set ofacceptable attributes. In this fashion, certain information specific tocertain types of emissions sources can be collected and, according tocertain embodiments, only that appropriate information can be enteredinto the system.

Once an identifier and data fields have been created for each emissionssource, emissions information relating to each source can be collected(block 12). That is, certain characteristics or information of eachtrackable emissions source may be associated with the identifier.

The information collected (block 12) for an emission source may varydepending on the type or category of emission source. For example, theemission sources may be placed into two categories: direct emissions andindirect emissions (as described above). Alternatively, the directemissions sources may be further placed into four subcategories based onthe four subtypes described above. Depending on the category and/orsubcategory of a source, the type of information collected, and thus thefields for which information may be collected, may differ. For example,the emission source information may include any emission sourceidentifying information such as the emission source identifier and typeand/or subtype of the emission source. In addition, the emission sourceinformation may include historical emissions data for the source (alsoreferred to as “legacy” data). Additionally, the information may includesite information relating to all of the sites where the enterprise hasemission sources, including site location, identification of emissionsources at the site, and any other relevant site information. If theemission source is one part of a system or group comprised of more thanone emission source, in some embodiments, the emission sourceinformation may include group information, including the group name,description of the group, identification of the emission sources in thegroup, along with any other relevant information. A group may comprise,for example, all of the emission sources at a particular site location.Additionally, for example, a group may comprise all of the emissionsources of an enterprise.

According to one embodiment, the process of collecting and storinginformation (block 12) relating to emission sources located at a site isimplemented using or in conjunction with a method or system forsurveying equipment assets located at a site or at multiple distributedsites. One example of such a system is disclosed in co-pending U.S.patent application Ser. No. 10/771,090, entitled “Site Equipment SurveyTool,” filed on Feb. 3, 2004, which is incorporated herein by referencein its entirety. FIG. 2 is a flow chart showing an equipment surveyingmethod 20 that allow for surveying equipment, including emissionssources, according to one embodiment. As shown in FIG. 2, the surveyingmethod 20 includes gathering and compiling legacy data for a client'sequipment assets, including the emissions sources (block 22), creatingan appropriate data structure for collecting and storing equipmentinformation (block 24), importing normalized legacy data into the datastructure (block 26), importing the data structure and the legacy data(block 28), and surveying site equipment assets to collect relevantinformation (block 30). In one embodiment, a quality control review isconducted on the collected survey data (block 32).

In one embodiment, an implementation of the system described herein isoperated in a similar fashion to, or in conjunction with, a enterpriseasset management system for managing the assets, including the emissionssources, of a distributed enterprise. One example of such a system isdisclosed in co-pending U.S. patent application Ser. No. 09/883,779,entitled “Method and System for Managing Enterprise Assets,” filed onJun. 18, 2001, which is incorporated herein by reference in itsentirety. FIG. 3 is a schematic diagram showing a network-basedemissions tracking system 50 according to a second embodiment. As shownin FIG. 3, the system 50 according to one embodiment can include aserver 52 in communication with client computers 54 and/or kiosks 56through a network 58. The client computers 54 and/or kiosks 56 can belocated at each of the various distributed sites. “Client computers” asused herein shall mean any known type of processor or computer. Thesystem 50 allows a distributed enterprise to monitor and track assets orequipment, emissions sources, and emissions at multiple sites.

As further shown in FIG. 3, in one embodiment, the server 52 is incommunication with an emissions source database 60 and a utilitiesdatabase 62. According to an alternative embodiment, the server 52 isalso in communication with an additional asset or equipment database 64that stores data relating to assets or equipment that are not emissionssources or data relating to all assets or equipment that is unrelated toemissions. Alternatively, the emissions source data, utilities data, andalternative asset or equipment data are maintained in a single database.

The client computers 54 are in communication with individual pieces ofequipment such as emissions sources through an asset/equipment interface66. In some embodiments, equipment interfaces 66 are attached to directemission sources with communications capabilities in order to monitorthe emissions production of the direct emission source. The equipmentinterface 66 can be configured to communicate with the equipment and toprovide a communication link between the equipment and a enterpriseprocessor 54 or the central processor 52.

In one embodiment, this interface 66 is configured to accept input fromemissions sensors. According to one implementation, the interface 66 isa local area wired or wireless network. In one aspect, the interface 66includes software to translate and normalize signals received fromvarious types of equipment, similar to that disclosed in co-pending U.S.patent application Ser. No. 10/734,725, filed on Dec. 12, 2003, which ishereby incorporated herein by reference in its entirety. In oneexemplary embodiment, the equipment interface to an emission sensor isan interface with a continuous emissions monitoring system such as theBaldwin™ Series Classic Thermo-Electric Cooler, available from ParmaPure LLC, located in Toms River, N.J.

In one aspect of the invention, an interface 66 associated with aparticular piece of equipment such as, for example, a direct emissionssource, allows for collection of information, including real-timeinformation, directly from the piece of equipment. Further, theinformation collected from the asset or piece of equipment can then beused in the present system in any fashion taught herein. In one example,given that the method and system of tracking, calculating, and reportingemissions described herein provides for tracking and calculatingemissions of any given asset, the information collected by theappropriate interface 66 can be used to calculate emissions of the pieceof equipment, the site, or the enterprise, according to one embodiment.

In the system 50, generally, emissions data entered into the system 50via a client computer or processor 54 and/or equipment interface 66 isreceived by the server 52 and stored in the emissions source database60.

The information relating to emission sources, according to oneembodiment, can be organized within the emission source database 60 orretrieved from the database 60 according to source, according to site,or any other desired parameter. That is, the information can be storedor retrieved on a per-site basis, a per-asset basis, or any other basis.For example, organizing information on a per-site basis allows forconsideration of all emission information at a site and processing ofthat information for purposes described herein. Alternatively,organizing the information on a per-source basis is also useful asdescribed herein.

The server or central processor 52 can be any computer known to thoseskilled in the art. In one embodiment, the central processor 52 includesa website hosted in at least one or more computer servers. These serversmay comprise web servers, database servers and/or application servers,which may run on a variety of platforms.

In one implementation, the central processor 52 includes softwareprograms or instructions that run on the server-side to process requestsand responses from an enterprise processor 54. These software programsor instructions send information to the enterprise processor 54, performcompilation and storage functions, and generate reports. According toone embodiment, the software programs or instructions are configured toperform the appropriate emissions calculations as described below. Thesoftware may be software applications commercially sold and normallyused by those skilled in the an or they may be specific applicationscoded in a standard programming language.

The central processor 52 allows access by the enterprise processor 54 tovarious network resources. In one embodiment, the central processor 52also has access, via the network 58 or some other communication link, toexternal data sources that may be used to keep the information in theserver current. In one implementation, a number of enterprise processors54 may be connected to the server at any given time, and therefore anumber of an enterprise's facilities or locations may utilize the systemsimultaneously.

According to one embodiment, the databases 60, 62, 64 may be of any typegenerally known in the art. The databases 60, 62, 64 may be integral tothe central processor 52 or they may be accessible to the centralprocessor 52 through a computer network or other suitable communicationlink. In one embodiment, the databases 60, 62, 64 are comprised of aplurality of database servers, some of which are integral to the centralprocessor 52, and some that are located remotely from the centralprocessor 52.

It is further understood that the client computers or enterpriseprocessors 54 may be any computer or computer systems used by thoseskilled in the art. Such enterprise processor 54 comprises a centralprocessor unit (“CPU”) and main memory, an input/output interface forcommunicating with various databases, files, programs, and networks(such as the Internet), and one or more storage devices. The storagedevices may be disk drive devices or CD-ROM devices. The enterpriseprocessor 54 may also have a monitor or other screen device and an inputdevice, such as a keyboard, a mouse, or a touch sensitive screen.

Generally, the emissions source database 60 includes any emission sourceinformation relating to the enterprise's emission sources, as describedabove. For example, the emission source information may include theemission source identifying information, historical emissions data, siteinformation, and, in some embodiments, group information. Alternatively,the database 60 can include any emission source information of any kind.

As discussed above, according to one embodiment, emissions data can becollected and entered into the system (block 12). According to oneembodiment, the system can store the emissions data in the emissionsdatabase 60. In one aspect, the emissions data includes informationrelating to the amount of emissions produced by an emission source. FIG.4 is a flow chart illustrating the process of collecting and enteringemissions data 12, according to certain embodiments. As shown in FIG. 4,in certain embodiments, a user identifies an emission source for whichinformation is to be collected (block 70). Alternatively, there is noneed to identify the emission sources because information is collectedfor all sources at a location. In some embodiments, based on the type ofemissions source identified, information corresponding to the identifiedsource is collected (block 72). After emission source information isgathered, the information is input into the system and associated withthe appropriate emission source (block 74). In one embodiment, theemissions information is collected and/or entered into the system on aperiodic basis.

The user, according to one embodiment, is an agent or employee of theenterprise. Alternatively, the user can be anyone with access to thesystem via a client computer 54.

It is understood that any relevant emissions source information can becollected. In one embodiment, the method of emissions informationcollection (block 72) and the type of information collected can dependon the type of emissions source. That is, different types of emissionssources may call for different information and different collectionmethods. For example, direct emissions source information is collectedin a different fashion than indirect emissions source information.

Returning to FIG. 4, one general method of collecting indirect or directemissions (block 72), according to one embodiment, includes collectingusage information. In the case of indirect emissions sources such asutilities, the utility provider provides to the enterprise an invoicerelating to the utility usage by the enterprise or by one particularlocation of the enterprise. Thus, the collection of usage informationrelating to such an indirect emissions source includes collecting theinvoice information (block 72). According to one embodiment, the invoiceinformation is collected by simply receiving a hardcopy of the invoice,for example by receiving the hardcopy in the U.S. mail. Alternatively,the invoice information is collected in an electronic format via ane-mail or other electronic form of communication, including at awebsite. In one example, the information of interest includes the totalutility usage.

Alternatively, the usage information can be collected via an interfacesimilar to the interface 66 described above with respect to FIG. 3. Inthis embodiment, the interface is coupled to an energy meter (such as,for example, an electric meter or a gas meter) to collect all usageinformation based on the meter. One example of such an interface is theData Manager™ available from Resource Data Management in Glasgow,Scotland.

For direct emissions sources, according to one embodiment, the emissionssource information can include total usage of the source during a givenperiod. Thus, the collection of information for direct emissions sourcescan also include the collection of usage information (block 72). Forexample, the direct emissions source can be a mobile combustion unitsuch as a vehicle, and the source information of interest can includethe total fuel usage during the period. In one aspect, the usageinformation is collected by manually collecting all fuel invoicesassociated with the source. Alternatively, the fuel invoice informationis collected in an electronic format via an e-mail or other electronicform of communication, including at a website.

In one aspect of the systems and methods disclosed herein, any invoicesor billing information can be managed and entered or processed via amethod or system similar to, or in cooperation with, one of the methodsor systems disclosed in co-pending U.S. application Ser. No. 11/423,860,filed on Jun. 13, 2006, which is hereby incorporated herein by referencein its entirety. FIG. 5 depicts one embodiment of a method forprocessing bills or invoices 80, in which the system 80 allows for entryand storage in a database of billing information at each site for eachemissions source or utility provider (block 82). The system furtherprovides for review and approval of each bill (block 84) and for paymentof each bill (block 86), including, in certain embodiments, paymentusing an electronic payment system.

As disclosed in that application, the billing information for entry andstorage (block 82) can include, but is not limited to, all theinformation provided in each periodic bill or invoice associated withany emissions source, such as a fuel bill relating to a direct emissionssource or a bill from a utility provider. For example, the billinginformation can include all fuel bills or other invoice information forany enterprise site relating to the operation of one or more directemissions sources and/or all invoice information for any enterprise siteprovided separately by one or more of the gas provider, electricityprovider, or any other utility or energy provider that results in theemission of GHGs. In one embodiment, the billing or invoice informationis entered manually by a user, such as an employee of the enterprise oran employee of the utility provider, at a client computer or kiosk orother entry point.

Alternatively, the information is entered electronically. For example,electronic entry can be accomplished by scanning a document with anyknown scanner utilizing OCR or any other scanning technology and loadingthe scanned information into the system. In another example, theinformation is entered electronically by direct electronic communicationbetween the billing system of the provider of the invoice and a systemas described herein over the network similar to the network described inFIG. 3. In a further alternative, the billing information iselectronically compiled by an external individual or individuals, suchas, for example, a third-party entity hired to compile the billinginformation into a format that can be easily loaded into the system andthen the billing information is loaded into the system. According to oneembodiment, the third-party individual or individuals compile historicalbilling information into an appropriate format for loading into thesystem. Alternatively, the third-party individual or individuals compilecurrent billing information on an on-going basis for loading into thesystem. In a further alternative, both historical and current billinginformation are compiled into an appropriate format by the third partyindividual or individuals or by an employee or agent of the enterprise.

For purposes of both direct and indirect emissions tracking, in additionto usage information and any other information relating to the amount ofemissions a source has produced, the user may enter any other relevantinformation (block 72), including but not limited to, the site where theemission source is located, the group that the emission source is a partof, if any, and the date the information was gathered.

In one embodiment, the indirect emissions source is electricity. Inanother embodiment, the indirect emissions source can be imported steam,imported heating, imported cooling, or any other imported energy sourcethat results in the emission of any GHGs. In one embodiment, theinformation gathered includes the total energy consumption of thesource. For example, if the indirect emissions source is electricity,the information to be collected can include the total electricityconsumption for some period in kilowatt hours. As discussed above, thisinformation can be collected or calculated from the electricity invoice.In another example, the indirect emissions source is imported steam,heating, or cooling. In this example, the information to be collectedcan include, but is not limited to, the total steam, heating, or coolingconsumption for some period in any appropriate unit of measure.

In one embodiment, the direct emissions source is a mobile combustionsource. In another embodiment, the direct emissions source can be astationary combustion source, a power plant, a manufacturing plant, orany other type of plant, asset, or equipment used at an enterpriselocation that emits any kind of GHGs at the location. In one embodiment,the information gathered includes the total energy consumption of thesource. For example, if the direct emissions source is a mobilecombustion source, the information to be collected can include any orall of the make and model of the source, the type of fuel consumed bythe source, the total fuel consumption of the source, and the distancetraveled by the source. As discussed above, this information can becollected or calculated from any or all of the fuel invoice(s), fuelpurchase records, odometer readings, trip manifests, and/or maintenancerecords. In another example, the direct emissions source is aco-generation plant as described above and the emissions sourceinformation that is collected can include the fuel input, electricityproduction, net heat production, and/or plant efficiency. In a furtherexample, the direct emissions source is a stationary combustion source,and the source information that is collected may include the type offuel consumed by the source and the total fuel consumption of thesource. This information can also be obtained from utility bills,according to one embodiment.

In another embodiment, the direct emissions source is a manufacturingprocess emission source, and the source information that can becollected includes total emissions of any measurable gas of interest inany appropriate unit of measure, including, for example, those gases andunits of measure set forth in EPA rules and government legislation.

According to one embodiment, the timing of the emissions informationcollection (block 72) and the number of such collections can varysignificantly. That is, the collection can be performed daily, weekly,monthly, yearly, or at any other known interval. Alternatively, thecollection can be performed randomly. It is also understood that thenumber of data points collected can vary significantly. That is, theemissions information can be based in one embodiment on only one invoicefor a broad emissions source category. Alternatively, the informationcan be based on one invoice for a subcategory of emissions sources. In afurther alternative, each emissions source is monitored individually bya user or dedicated interface or sensor.

In another embodiment, fugitive emissions can also be tracked. Thefugitive emissions source can be any of a number of assets or equipmentthat leaks any GHG. In one example, the fugitive emissions source isrefrigeration equipment, and the source information that can becollected includes the equipment type, the actual and/or calculated leakrate, and/or the quantity and type of refrigerant used.

According to one embodiment, the tracking and management of fugitiveemissions can be performed via a method and system similar to thatdescribed in co-pending U.S. application Ser. No. 10/429,619, filed onMay 5, 2003, which is hereby incorporated herein by reference in itsentirety. The application discloses tracking and management of fugitiveemissions such as refrigerant leakage, and it is understood that theteachings can apply to any type of fugitive emissions.

For either or both of direct and indirect emissions tracking, theemissions source information is then entered into the system (block 74).In one implementation, the information is manually entered by a user.For example, a user could enter the information from a hardcopy invoiceinto the system using a client computer. Alternatively, the informationis automatically entered into the system. For example, the informationis provided in electronic format and is automatically loaded into thesystem upon receipt or retrieval from the provider of the invoice.

In an alternative embodiment, any emission source information can beentered into the system via an equipment interface similar to theinterface discussed above with respect to FIG. 3. The equipmentinterface allows the system to automatically track information relatedto the amount of emissions produced by a certain emission source withoutany manual input or effort by a user. For example, a stationarycombustion source, such as a smokestack, may be equipped with anequipment interface that continuously measures the amount of emissionsproduced by the source and is equipped with a communication link betweenthe source and the central processor. Any information received by thecentral processor from the equipment interface may then be stored in thedatabase.

In a particular embodiment, the system saves into an emissions database,such as a database similar to the one discussed above with respect toFIG. 3, all of the information gathered such that the system accumulatesall of the information relating to the amount of emissions produced byeach emission source.

Returning to FIG. 1, certain embodiments of the method of trackingemissions include calculating the amount of emissions produced by anemission source or sources (block 14). That is, the amount of emissionsproduced, particularly the amount of greenhouse gas emissions, and moreparticularly the amount of CO2 and CO2 equivalents, produced by aparticular source or group of sources can be calculated for any desiredtime period. In certain embodiments, the system calculates the emissionsproduced by an entire site and/or the entire enterprise. In otherembodiments, the system automatically performs calculations and orreports emission totals at recurring predetermined intervals, such asevery month or every year.

In one aspect, the amount of emissions is calculated in the system byinputting into an appropriate equation emissions information stored inthe database and emission factors appropriate to the source for which anemission production amount is to be calculated. For purposes of thepresent application, “emission factors” are representative values thatrelate the quantity of emissions released to the atmosphere with anactivity associated with the release of emissions. These factors areexpressed as the weight of emission (typically Metric Ton of CO2 dividedby a unit weight, volume, distance, or duration of the activityproducing the emission). Emission factors are made available throughvarious governmental agencies, such as, for example, theIntergovernmental Panel on Climate Change (“IPCC”) or EnvironmentalProtection Agency. Because the emission factors fluctuate, in someembodiments, they are updated on a periodic basis.

One example of an emissions factor is the factor associated withindirect emission sources, such as those sources provided by utilities.One common term for such a factor is the “eGRID factor.” This factor isassigned to an energy provider or utility based on the emissions createdby the provider, which is influenced by the sources of the energy. Forexample, an electricity provider that utilizes solely coal plants togenerate electricity would generate significantly more emissions than aprovider that utilizes solely windmills to generate electricity, andthus the factor assigned to each would reflect that difference inemissions. Thus, an emissions factor would be included in anycalculation relating to an indirect emissions source.

In a further example of an emissions factor, if the emission source is aco-generation plant or system utilized by a third party energy orutility provider (and thus is an indirect emissions source), oneemission factor of note relates to the calculation of emissions of theenterprise relating to energy acquired from a third party provider usingsuch a co-generation plant or system. That is, a co-generation plant orsystem's simultaneous generation of power and useful heat creates a needfor a factor or formula that accounts for such simultaneous generationand provides a relatively accurate estimate of the emissions associatedwith energy utilized by the enterprise. According to one implementation,one such calculation is the coefficient of performance, which reflectsthe relationship of useful heat generated by a co-generation plant orsystem to the power consumed to generate that heat. The equation forthis particular coefficient can be expressed as follows:

$\begin{matrix}{{COP}_{\max} = \left( \frac{Q_{low}}{Q_{high} - Q_{low}} \right)_{\max}} \\{= \frac{Q_{low}}{{Q_{low}\frac{T_{high}}{T_{low}}} - Q_{low}}} \\{= \frac{T_{low}}{T_{high} - T_{low}}}\end{matrix}$

According to one embodiment, the amount of emissions produced iscalculated in the system using the following general equation:

Emissions Produced=Emission Activity [weight, volume, distance, orduration]×Emission Factor [Metric Ton C0₂/(weight, volume, distance, orduration)]

That is, the processor, according to one embodiment, performs thecalculation based on the above equation to determine the amount ofemissions produced by a particular emissions source.

For example, if the emission source is purchased electricity, the amountof CO₂ produced is calculated by the system using the followingequation:

Emissions Produced=Electricity consumed [kWh]×Emission Factor [MetricTon C02/kWh].

As another example, if the emission source is an stationary combustionsource that consumes natural gas, the amount of CO₂ produced iscalculated by the system using the following equation:

Emissions Produced=Natural gas consumed [Therms]×Emission Factor [MetricTon C02/Therm].

Further emissions totals can be calculated by the system using any ofthe equations and factors provided in the GHG protocol by the WorldResources Institute (www.ghgprotocol.org), which is hereby incorporatedherein by reference in its entirety. Plus, further calculations,equations, and emissions factors relating to GHG emissions are set forthin the California Climate Action Registry General Reporting Protocol,Version 2.1, published in June, 2006, which is hereby incorporatedherein by reference in its entirety. In addition, the emissions totalscan be attained using any known equations or calculations fordetermining emissions, any or all of which can be integrated into thesoftware of the system. For example, according to one embodiment, thecalculations and equations are integrated into the software of a centralprocessor similar to the central processor described with respect toFIG. 3.

In accordance with another embodiment, a method and system for trackingand/or reporting emissions can include tracking the emission of CH₄and/or N₂O from an emission source. In a further embodiment, the methodor system can include converting the CH₄ and/or N₂O emissions into “CO₂equivalents.” According to one embodiment, the conversion isaccomplished on the basis of the respective global warming potentials(“GWPs”) of the CH₄ and/or N₂O emissions. “GWPs,” as used herein, arerepresentative values used to compare the abilities of differentgreenhouse gases to trap heat in the atmosphere. The GWP values providea construct for converting emissions of various gases into a commonmeasure denominated in CO₂ equivalent (“CO₂e”) and is provided by theIPCC. According to one embodiment, the server of the system performs theconversion based on the above construct.

In one embodiment, the conversion equation is set forth as follows:

Metric Tons of CO₂ e=Metric Tons of Non-CO₂ e GHG×GWP.

The 1996 and 2001 GWP numbers are set forth in Table 1, which waspublished in the California Climate Action Registry General ReportingProtocol, discussed and incorporated above.

TABLE 1 Greenhouse GWP GWP Gas (SAR, 1996) (TAA, 2001) CO₂ 1 1 CH₄ 21 23N₂0 310 296 HFC-123 11,700 12,000 HFC-125 2,800 3,400 HFC-134a 1,3001,300 HFC-143a 3,800 4,300 HFC-152a 140 4120 HFC-227ea 2,900 3,500HFC-236fa 6,300 9,400 HFC-43-10-mee 1,300 1,500 CF₄ 6,500 5,700 C2F69,200 11,900 C3F8 7,000 8,600 C3F10 7,000 8,600 C4F12 7,500 8,900 C6F147,400 9,000 SF6 23,900 22,000 Source U.S. Environmental ProtectionAgency, US Greenhouse gas Emissions and Sinks: 1990-2000 (April 2002)

It is understood that the GWP values are merely one estimate to capturethe ability of each GHG to trap heat and are occasionally modified bythe IPCC. In alternative embodiments, other measures and othercalculations could be used to calculate CO2 equivalents or other typesof equivalents. In a further embodiment, emissions can be measured andtracked without calculating any equivalents.

In accordance with a further implementation, certain systems and methodsdescribed herein can provide for tracking and managing tradable creditsrelating to greenhouse gases, including carbon credits. “Carboncredits,” as used herein, shall mean any tradable commodity that assignsa value to GHG emissions. It is understood that there are currently twoexchanges for carbon credits: the Chicago Climate Exchange and theEuropean Climate Exchange. It is further understood that certain quotashave been established by the Kyoto Protocol and countries around theworld relating to the amount of GHG emissions that countries andbusinesses can produce, and that each business can compare its emissionsto its quota to determine whether it has a credit surplus (because itsemissions were below its quota) or it has a credit debt (because itsemissions exceeded its quota), and act accordingly.

According to one embodiment, one method and system of tracking andmanaging carbon credits for an enterprise 90 is set forth in FIG. 6. Itis understood that this method and system can be performed on the basisof a site or an entire enterprise. Alternatively, the method and systemcan be performed on the basis of a grouping of sites, such as all thesites in a particular state or region. It is also understood that themethods and systems described herein are not limited to tracking and/ormanagement of carbon credits or the climate exchanges described aboveand can be used to track and manage any type of tradable credit relatingto GHG emissions.

First, as set forth in FIG. 6, the system provides for calculating theemissions totals (block 92) in a fashion similar to the emissionscalculations provided with respect to block 14 in FIG. 1 and discussedabove. Then, the system provides for comparing the emissions totals tothe predetermined quota for the site or enterprise (or other measure, asdiscussed above) and calculating whether the emissions for that site orenterprise exceed the quota (block 94). Based on this calculation, thesystem or method provides for calculating the carbon credit debt orsurplus (block 96). That is, if the site or enterprise has exceeded itsemissions quota, then it has a carbon credit debt. In contrast, if thesite or enterprise has emitted less than its quota, then it has a carboncredit surplus.

According to one embodiment, the system 90 then allows for the purchase,sale, or reallocation of credits (block 98) depending on whether thereis a surplus or debt. That is, if there is a credit debt, the systemcalculates the number of credits that must be purchased to eliminate thedebt. In one implementation, the system is connected via a networkconnection or other communication link to an external source thatprovides the current market price for a credit and utilizes thatinformation to calculate the cost of purchasing the required credits. Inanother embodiment, the system provides for or automatically performs apurchase of the required credits.

If there is a credit surplus, the system 90 calculates the creditsurplus (the number of credits that the site or enterprise has to sparebecause it did not exceed its emissions quota). In another embodiment,the system 90 also utilizes the communication link to calculate thevalue of the surplus credits. In another embodiment, the system providesfor or automatically performs a sale of the surplus credits.

Alternatively, in an embodiment in which the system 90 calculates acredit surplus at one or more sites of an enterprise and furthercalculates a credit debt at one or more other sites of the enterprise,the system can provide for calculating each of the surpluses and thedebts and reallocating the credits from the surplus sites to the debtsites, thereby eliminating at least a portion of the need to purchaseadditional credits on the market.

In a further alternative step, the system 90 also can provide for theadjustment of current or future emissions based on the calculations of acredit debt or credit surplus (block 100). Such adjustment can beimplemented with the predictive capabilities discussed below.

In one aspect, a processor in the system 90 has software configured toperform the above comparisons and calculations.

In another embodiment, certain systems and methods described herein canprovide for predictive analysis and preventative planning based on theemissions information and calculations described above, includingpredictive analysis and planning and/or adjustment of emissions based onthe calculations of credit surplus or debt as described above. In oneembodiment, such a system or method is similar to or operated inconjunction with one of the systems and methods providing predictiveanalysis and preventative planning as described in U.S. application Ser.No. 11/423,860, which is discussed and incorporated by reference above.Such a system or method could include software that draws upon thecalculations discussed above to predict future trends in the data. Theenterprise or a user can then utilize a predicted trend and the aboveinformation to take appropriate steps to address any predicted impact ofthe trend. According to one exemplary embodiment, predicted weatherpatterns can be used to predict a trend in energy use and thus GHGemissions. For example, perhaps a particularly cold winter has beenpredicted. The system, according to one embodiment, can compare thepredicted winter season with past correlations and/or calculatedcorrelations between similar winter seasons and GHG emissions. Based onthe correlations, the system can predict the impact of the cold winterseason on the amount of GHG emissions for a site or a group of sites inthe region impacted by the cold weather.

In another exemplary embodiment in which each site has been mapped withGIS capabilities as disclosed in U.S. application Ser. No. 10/771,090,which is incorporated herein by reference in its entirety, the systemcan compare a predicted path of a weather event (such as a cold snap orheat wave, etc.) with site locations using a map-based interface andidentify the sites of the enterprise predicted to be directly affectedby the weather. The system can further calculate and/or notify a user orusers of the predicted GHG emissions. In another exemplary embodiment, apredicted temperature spike across a certain region can be used topredict expected GHG emissions relating to electricity, etc.

According to one embodiment, preventative action can then be taken bythe user or the enterprise based on the predicted information providedby the system. In one embodiment, the user takes action based on thepredicted information provided by the system. In the example of thepredicted winter season, the user can take such steps as reducing energyconsumption and thereby reducing emissions at unaffected sites inanticipation of increased emissions at the affected sites, or any otherappropriate action to prepare for the expected increase in emissions.

Alternatively, the preventative action is implemented by the system.That is, the system allows for data and predictive analysis, includingpredicting certain trends relating to certain assets or equipment, andupon the triggering of a certain event associated with thosepredictions, electronically communicating or transmitting operatinginstructions to the relevant piece of equipment via the asset/equipmentinterface associated with that piece of equipment, similar to thatdescribed above with respect to FIG. 3. Thus, the asset/equipmentinterface capabilities can be used in conjunction with the data andpredictive analysis capabilities as described above to provide forpreventative action or action to address the impact of a predictedtrend.

In one embodiment, the asset/equipment interface capabilities can beutilized to remotely control operating parameters of certain energy orenergy-related systems at a site, as disclosed in further detail in U.S.application Ser. No. 10/734,725, which is mentioned and incorporated byreference above, to accomplish measures intended to prevent or reduceany negative impact of predicted phenomenon as described above. Thus,the system according to one embodiment allows for tracking variousparameters relating to equipment at a site or multiple sites, performingdata and predictive analysis, and upon the triggering of a certain eventor predicted event associated with those parameters, electronicallycommunicating or transmitting operating instructions to the equipment tothereby impact GHG emissions in some way. According to one embodiment,the types of equipment that can be remotely controlled in this fashioninclude, but are not limited to, refrigeration, lighting, and HVACequipment and systems, or any other GHG emitting equipment of any kind.

In the example of the predicted cold winter season, the predicted coldtemperatures can trigger the system to electronically communicateinstructions to the HVAC systems and, in some embodiments, additionalpower consuming systems of unaffected sites to reduce power output ofthose systems, thereby reducing the GHG emissions associated with thatequipment, which, in some embodiments, allows the enterprise to conserveGHG credits in any GHG credit market that may be established by anorganization or government such as the carbon credit market describedabove. In the example of the predicted temperature spike, the predictedhigh temperatures could trigger the system to electronically communicateinstructions to the HVAC systems of unaffected sites to reduce poweroutput of those systems, thereby reducing the GHG emissions at thosesites and, in some embodiments, conserving the enterprise's GHG creditsto compensate for the increased emissions at the affected sites.

In either of the above examples, the instructions transmitted by thesystem can be further impacted by the system's consideration andanalysis of the market demand information and GHG credit rateinformation in addition to the predicted weather trends. According toone embodiment, the predicted weather pattern results in a predicteddemand and/or GHG credit rate that triggers instructions transmitted bythe system to the relevant equipment through the appropriate interfaceor interfaces based on the predicted rate. Alternatively, real-time ornearly real-time rate information can be inputted into the system of thepresent embodiment and based on the GHG credit rate, the system can betriggered to transmit various instructions from the system to therelevant equipment through the appropriate interface or interfaces. Forexample, in the cold temperature example above, the server software maypredict a certain GHG credit rate that triggers an electronicinstruction to be transmitted to the equipment at the affected site orsites instructing the HVAC systems to reduce output by somepredetermined percentage during the predicted peak rate period(s) toreduce emissions and thus the expense of the GHG credits required forthose emissions. Thus, the market demand and GHG credit rate informationcan be taken into account in providing instructions to the relevantequipment and/or sites. In a farther alternative, the system can betriggered by any number of different parameters to communicate withvarious equipment to implement preventative or remedial actions inresponse to a predicted trend.

According to one embodiment, the method and/or system can generateemission reports (block 16 of FIG. 1). Generally, an emission report caninclude any desired information about an identified emission source orgroup of emission sources, including without limitation, the emissionsource identifier, the type and/or subtype, the site location, and thetotal amount of emissions produced. According to one embodiment, thetotal amount of emissions includes the amount of GHGs produced.Alternatively, the total amount of emissions includes the amount of CO2and CO2e produced, expressed in metric tons of carbon dioxide.

FIG. 7 depicts one method of generating an emissions report 16,according to one implementation. This particular method includesselecting a time period over which emissions production is to becalculated (block 102), selecting a particular emission source or groupof emission sources for which emission production is to be calculated(block 104), generating an emission report on the basis of the selectedtime period and selected emission sources (block 106), and making thereport available for dissemination (block 108).

A report may be requested for any time period (block 102), according toone embodiment. For example, an emissions report may be requested forthe amount of emissions produced in the preceding day, week, month, oryear. Alternatively, a report may be requested for any time period.

A report may also be requested for any emissions source or any group ofemissions sources (block 104), according to one implementation. Forexample, in some embodiments, a report request may be made for all of anenterprise's emission sources. Alternatively, a report request may bemade on the basis of site location, source type or subtype, or anycombination thereof.

Typically, a report request is initiated by a user located at a remotesite through the use of an enterprise processor or client computersimilar to those in FIG. 3. Alternatively, the request can be initiatedby anyone with access to the system. For example, the request could berequested by any user with access to the system over the interne.

Upon initiation, according to one embodiment, the server utilizes theparameters provided by the user to retrieve the appropriate informationfrom emissions source database and generate the report (block 106).Subsequently, the emissions report can be made available fordissemination (block 108). In some embodiments, the report is only madeavailable for dissemination within the enterprise internally. Forexample, the report may be automatically distributed to predeterminedrecipients within the enterprise. Alternatively, the report may, inaccordance with applicable laws and regulations, be made available fordissemination to individuals or entities external to the enterprise,such as, for example, local, state, or federal governmental agencies. Inone embodiment, the report is generated and distributed in hardcopy.Alternatively, the report is generated and distributed electronically,such as via e-mail or a webpage. In a further alternative, the reportcan be generated in any known form and any known fashion.

Although certain inventions have been described herein with reference topreferred embodiments, persons skilled in the art will recognize thatchanges may be made in form and detail without departing from the spiritand scope of those inventions.

1. A network-based emissions tracking system for an enterprise, thesystem comprising: (a) a central processor accessible on a computernetwork; (b) an asset database in communication with the centralprocessor, the asset database configured to store: (i) asset informationrelating to a plurality of assets at a plurality of locations, whereinthe plurality of assets comprises at least one indirect emissions assetpowered at least in part by at least a first indirect emissions source;and (ii) usage information relating to each of the plurality of assets;(c) a client processor in communication with the central processor, theclient processor configured to allow for inputting to the asset databaseany portion of the asset information and the usage information; and (d)emissions tracking software associated with the central processor, theemissions tracking software configured to calculate and track acalculated greenhouse gas emissions amount relating to the at least oneindirect emissions asset based on the usage information and a factorassociated with the first indirect emissions source.
 2. The system ofclaim 1, wherein the first indirect emissions source comprises anelectricity provider.
 3. The system of claim 2, wherein the electricityprovider comprises at least one coal plant or at least one windmill. 4.The system of claim 1, wherein the first indirect emissions sourcecomprises a steam provider or a heat provider.
 5. The system of claim 1,wherein the factor associated with the first indirect emissions sourceis an eGRID factor.
 6. The system of claim 1, wherein the emissionstracking software is further configured to calculate and track thecalculated greenhouse gas emissions amount relating to all of the atleast one indirect emissions assets based on the usage information andthe factor associated with at least the first indirect emissions source.7. The system of claim 1, further comprising at least a second indirectemissions source, wherein the at least one indirect emissions asset isfurther configured to be powered at least in part by the second indirectemissions source.
 8. The system of claim 7, wherein the emissionstracking software is further configured to calculate and track thecalculated greenhouse gas emissions amount relating to the at least oneindirect emissions asset based on the usage information, the factorassociated with the first indirect emissions source, and a factorassociated with a second indirect emissions source.
 9. The system ofclaim 1, wherein the plurality of assets further comprises at least onedirect emissions asset.
 10. The system of claim 9, wherein the emissionstracking software is further configured to calculate and track an actualgreenhouse gas emissions amount relating to the at least one directemissions asset based on the usage information and a factor associatedwith the at least one direct emissions asset.
 11. A network-basedemissions tracking system for tracking emissions of a plurality ofassets located at a plurality of locations of an enterprise, the systemcomprising: (a) a central processor accessible on a computer network;(b) an asset database in communication with the central processor, theasset database configured to store: (i) asset information relating tothe plurality of assets located at the plurality of locations, whereinthe plurality of assets comprises: (1) at least one indirect emissionsasset powered at least in part by at least a first indirect emissionssource; and (2) at least one direct emissions asset; and (ii) usageinformation relating to each of the plurality of assets; (c) a clientprocessor in communication with the central processor, the clientprocessor configured to allow for inputting to the asset database anyportion of the asset information and the usage information; and (d)emissions tracking software associated with the central processor, theemissions tracking software configured to (i) calculate and track anactual greenhouse gas emissions amount relating to the at least onedirect emissions asset; and (ii) calculate and track a calculatedgreenhouse gas emissions amount relating to the at least one indirectemissions asset based on the usage information and a factor associatedwith the first indirect emissions source.
 12. The system of claim 11,wherein the emissions tracking software is further configured to (a)calculate and track the actual greenhouse gas emissions amount relatingto all of the at least one direct emissions assets at a particularlocation of the plurality of locations; and (b) calculate and track thecalculated greenhouse gas emissions amount relating to all of the atleast one indirect emissions assets at the particular location of theplurality of locations.
 13. The system of claim 11, wherein theemissions tracking software is further configured to calculate and tracka total greenhouse gas emissions amount relating to all of the assets ata particular location of the plurality of locations.
 14. The system ofclaim 11, wherein the emissions tracking software is further configuredto calculate and track a total greenhouse gas emissions amount relatingto all of the plurality of locations.
 15. The system of claim 11,wherein the emissions tracking software is further configured tocalculate and track a total greenhouse gas emissions amount relating tothe enterprise.
 16. A network-based emissions tracking system for anenterprise, the system comprising: (a) a central processor accessible ona computer network; (b) an asset database in communication with thecentral processor, the asset database configured to store: (i) assetinformation relating to a plurality of assets at a plurality oflocations, wherein the plurality of assets comprises at least onevehicle; and (ii) usage information relating to each of the plurality ofassets; (c) a client processor in communication with the centralprocessor, the client processor configured to allow for inputting to theasset database any portion of the asset information and the usageinformation; and (d) emissions tracking software associated with thecentral processor, the emissions tracking software configured tocalculate and track a greenhouse gas emissions amount relating to the atleast one vehicle.
 17. The system of claim 16, wherein the emissionstracking software is further configured to calculate and track an actualgreenhouse gas emissions amount relating to at least one of the at leastone vehicles.
 18. The system of claim 16, wherein the emissions trackingsoftware is further configured to calculate and track a calculatedgreenhouse gas emissions amount relating to at least one of the at leastone vehicles.
 19. The system of claim 16, wherein the emissions trackingsoftware is further configured to calculate and track a total greenhousegas emissions amount relating to all of the at least one vehicles basedat a particular location.
 20. The system of claim 16, wherein the atleast one vehicle comprises at least one of a truck, a ship, a train, oran airplane.